Skip to content

fix(lock): honor SOURCE_DATE_EPOCH in lock timestamps - #33

Merged
HaoZeke merged 1 commit into
mainfrom
fix/lock-source-date-epoch
Nov 16, 2026
Merged

HaoZeke merged 1 commit into
mainfrom
fix/lock-source-date-epoch

Conversation

@HaoZeke

@HaoZeke HaoZeke commented Nov 16, 2026

Copy link
Copy Markdown
Collaborator

A lock's timestamp now follows SOURCE_DATE_EPOCH when that variable is a number of seconds.

  • Both lock writers used the current UTC time, so two solves of the same inputs wrote different timestamps. The time is now SOURCE_DATE_EPOCH when it is a decimal number of seconds since the Unix epoch, in UTC. An empty or non-numeric value still uses the current time.

source_date_epoch_is_the_lock_timestamp checks that 1700000000 is written as 2023-11-14T22:13:20Z on two solves, and that a non-numeric value is not that stamp. The commit has a towncrier fragment.

@HaoZeke
HaoZeke merged commit 17f4bbc into main Nov 16, 2026
21 checks passed
@HaoZeke
HaoZeke deleted the fix/lock-source-date-epoch branch November 16, 2026 05:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant